Feature Additions 10.x Schema

For all 10.x family of schema, all transactions require the id attribute. Also, all linked transactions (i.e., transactions that use the <litleTxnId> to reference the parent transaction) return a response code of 001 - Transaction Received in the XML response message. You must either pick-up the Declined Transaction SSR report, or view the Declined transaction report in the eComm iQ to determine the final disposition of the transaction.

The following features and capabilities were added to the 10.x schema family.

Many of the features/capabilities add to the V10.x versions were also back-ported to the later versions in the V9.x stream (see previous section).

  • New Status Query transaction type (10.0) - This new transaction type allows you to verify the receipt and status of a submitted transaction.

  • Support for Android Pay (10.1/10.2) - The schema file were modified to support Android Pay In-App purchases in version 10.1, but the new capability was not generally available until the 10.2 release.

  • New Funding Instruction Void transaction (10.1) - Allows you to void an unsettled Dynamic Payout Funding Instruction.

  • Support for Sessionless Advanced Fraud Tool option (10.3) - The new capability allows the use of Advanced Fraud Tools without the submission of the <threatMetrixSessionId> element. With this option, the fraud check only involves Worldpay submitted data points and any custom attributes submitted by the merchant.

  • Support for SEPA (Single Euro Payments Area) Direct Debit (V10.4) - Support was added for the SEPA method of payment in Online Sale transactions. SEPA allows for the direct debit of accounts for Euro-to-Euro transactions, adding to our International offering.

  • Return several network ISO 8583 fields in Enhanced Auth Response (10.4) - The new capability returns data from seventeen fields of the ISO 8583 network response messages. This provides additional data points for transactional analysis.

  • Custom Identifier element added to PayFac Dynamic Payout instructions (10.4) - Support added for <customIdentifier> element in Dynamic Payout funding instructions. Payment Facilitators can use this element to specify a Billing Descriptor to appear on the bank statements of the parties involved in the funds transfer. The information you provide in this element populates the Individual ID field of the ACH Record. The use of this field and its appearance on bank statements is at the discretion of the bank producing the statement.

  • Support for 8-digit Canadian eCheck Routing Numbers (10.5) - The minLength of the <routingNum> was changed from 9 to 8.

  • Support for Visa and Discover Recurring Payments using networkTransactionId (10.5) - For recurring payments involving network tokens (i.e., Apple Pay and Android Pay), Visa and Discover return a <networkTransactionId>, which the merchant must include in subsequent recurring payments as a reference to the original transaction.

  • Support for return of eciIndicator in Android Pay response (10.6) - The <eciIndicator> element was added to the <androidpayResponse> element.

  • Added orderId to Account Updater response (10.7) - Added <orderId> to Account Update response message, which had been removed previously in V10.

  • Added support for Card on File transactions (10.8) - The following values were added to the <processingType> element enumerations: initialCOF, merchantInitiatedCOF, and cardholderInitiatedCOF.

  • Added authIndicator to support Incremental Auths (10.10) - used by certain Travel and Entertainment (T&E) merchants when final purchase amounts are unknown.

  • Added foreignRetailIndicator to capture parent elements (10.10) - must be present when the marketplace and retailer are not in the same region (country).